\section{Conclusion}
To summarize the collected information and results of the tests, it can be said,
that on the one hand it is not possible to build a handmade kernel, which can
compete with a real-time kernel. At this point it has to be mentioned,
that the selfmade kernel was build up in a couple of weeks and the
real-time kernel based on Ubuntu gets developed since years. On the other hand,
the statement can be made, that the self patched kernel is much more reliable
than the standard kernel of the Ubuntu distribution.


Moreover another result of this paper, is that activating the real-time
capabilities are quite easy. This can be underlined by the short instructions
the paper gives. 


The significant results from testing several kernels on different machines
leads to the statement that the latency value of a real-time system compared to
a non-real-time system is much less. If the system is under load (e.g. during
the pi\_stress test), the different latencies between the two systems become
more obvious.


Furthermore the two different schedulers in the cyclictest which
make it possbile to operate with or without priority are not optimized for
real-time systems. Therefore the question arises how the behavior of the test
and the corresponding results would change, if the option of activating a
optimized real-time scheduling algorithm would lead to other results.


Another interesting but confusing result of this paper and the related test
cases, is that only minimal differences during the cyclictest
between switching priority on and off have been measured. The estimated
values while testing with activated and deactivated priority were
nearly the same.


Additional to that, the fact has to be mentioned that during the cyclictest with
deactivated the mlock-option, the last threads did not even get one single
cycle. Regarding to real-time requirements and especially the application
area of real-time systems this result is a shattering one for the
real-time kernel.


These disillusioning facts and results which were discovered put the question
in foreground ''Does a Linux real-time kernel really fulfill all real-time
requirements?''.